Skip to content

Conversation

@jmmv
Copy link
Contributor

@jmmv jmmv commented May 27, 2025

To do this, recognize new tools/bazel.<OSNAME>-<ARCH> and tools/bazel.<ARCH> names for the wrapper, and favor those over tools/bazel if they are present.

@jmmv
Copy link
Contributor Author

jmmv commented Jun 19, 2025

I pushed a new version of the change to (try to) fix the problems with the Windows tests... but now one of the Windows jobs fails with:

external\gazelle++go_deps+org_golang_x_sys\unix\vgetrandom_linux.go:7:9: file requires newer Go version go1.24
compilepkg: error running subcommand external\rules_go++go_sdk+bazelisk__download_0\pkg\tool\windows_amd64\compile.exe: exit status 2

which seems unrelated to my change given that it's coming from a dependency. (I'm not even sure why the Windows build would look into a file with linux in its name, but, well, Go.)

To do this, recognize new tools/bazel.<OSNAME>-<ARCH> and tools/bazel.<ARCH>
names for the wrapper, and favor those over tools/bazel if they are present.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants